sumo compilation
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: task do_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: task do_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching file misc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.
Sinan
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 26 lines · ---- Sinan Kaya
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc Applying patch misc_create_inode.c-label_rootfs.patch
patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Exactly the same issue since September.
Here is my discussion
https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html.
With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected]> ha scritto:
Quoted 46 lines
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 5 lines · ---- Sinan Kaya
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo
branch?
Quoted 5 lines
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/
e2fsprogs_1.43.8.bb:do_patch)
Quoted 3 lines
NOTE: recipe e2fsprogs-native-1.43.8-r0: task
do_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:
do_patch)Quoted 2 lines
NOTE: recipe e2fsprogs-1.43.8-r0: task
do_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt--quiltrc
Quoted 11 lines
Applying patch misc_create_inode.c-label_rootfs.patch patching file
misc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilation
Exactly the same issue since September.
Here is my discussion https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html. With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected] <mailto:[email protected]> > ha scritto:
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 26 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] <mailto:[email protected]> https://lists.yoctoproject.org/listinfo/yocto
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] <mailto:[email protected]> https://lists.yoctoproject.org/listinfo/yocto
CC'ing the selinux maintainers:
I was told that using the master branch and reverting the e2fs change
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151) works on sumo.
Stefano's suggestion unfortunately didn't work.
Maybe, it is time to create the sumo branch?
Quoted 57 lines · Steve Scott
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilationExactly the same issue since September.
Here is my discussion https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html. With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected] <mailto:[email protected]> > ha scritto:
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 26 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] <mailto:[email protected]> https://lists.yoctoproject.org/listinfo/yocto
Sorry for confusing names, not enough coffee yet...
I was trying to say that Steve's suggestion to use
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
didn't work on sumo branch.
Quoted 64 lines · Sinan Kaya
CC'ing the selinux maintainers:
I was told that using the master branch and reverting the e2fs change
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151) works on sumo.Stefano's suggestion unfortunately didn't work.
Maybe, it is time to create the sumo branch?
Quoted 53 lines · Steve Scott
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilationExactly the same issue since September.
Here is my discussion https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html. With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected] <mailto:[email protected]> > ha scritto:
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 26 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] <mailto:[email protected]> https://lists.yoctoproject.org/listinfo/yocto
You may also need
PREFERRED_PROVIDER_virtual/refpolicy = "refpolicy-standard"
in local.conf.
-steve
Quoted 92 lines
-----Original Message-----
From: Sinan Kaya [mailto:[email protected]]
Sent: Thursday, October 18, 2018 8:06 AM
To: [email protected]; 'Stefano Cappa' <[email protected]>
Cc: [email protected]
Subject: Re: [yocto] [selinux] sumo compilationSorry for confusing names, not enough coffee yet...
I was trying to say that Steve's suggestion to use
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
didn't work on sumo branch.
Quoted 7 lines · Sinan Kaya
CC'ing the selinux maintainers:
I was told that using the master branch and reverting the e2fs change
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151)
works on sumo.Quoted 20 lines
Stefano's suggestion unfortunately didn't work.
Maybe, it is time to create the sumo branch?
Quoted 15 lines · Steve Scott
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilationExactly the same issue since September.
Here is my discussion
https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html.
Quoted 9 lines
Quoted 9 lines
With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected]
<mailto:[email protected]> > ha
scritto:It was broken in rocko too. I added this to local.conf to workaround the
problem:
Quoted 11 lines
Quoted 11 lines
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 5 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo
branch?
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fspr ogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:d
Quoted 16 lines
Quoted 15 lines
Quoted 14 lines
o_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc Applying patch misc_create_inode.c-label_rootfs.patch patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
--
_______________________________________________
yocto mailing list
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto
Thanks Steve,
We'll give it a try.
Quoted 100 lines · Steve Scott
You may also need
PREFERRED_PROVIDER_virtual/refpolicy = "refpolicy-standard"
in local.conf.-steve
Quoted 92 lines
-----Original Message-----
From: Sinan Kaya [mailto:[email protected]]
Sent: Thursday, October 18, 2018 8:06 AM
To: [email protected]; 'Stefano Cappa' <[email protected]>
Cc: [email protected]
Subject: Re: [yocto] [selinux] sumo compilationSorry for confusing names, not enough coffee yet...
I was trying to say that Steve's suggestion to use
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
didn't work on sumo branch.
Quoted 7 lines · Sinan Kaya
CC'ing the selinux maintainers:
I was told that using the master branch and reverting the e2fs change
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151)
works on sumo.Quoted 20 lines
Stefano's suggestion unfortunately didn't work.
Maybe, it is time to create the sumo branch?
Quoted 15 lines · Steve Scott
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilationExactly the same issue since September.
Here is my discussion
https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html.
Quoted 9 lines
Quoted 9 lines
With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected]
<mailto:[email protected]> > ha
scritto:It was broken in rocko too. I added this to local.conf to workaround the
problem:
Quoted 11 lines
Quoted 11 lines
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 5 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo
branch?
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fspr ogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:d
Quoted 16 lines
Quoted 15 lines
Quoted 14 lines
o_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc Applying patch misc_create_inode.c-label_rootfs.patch patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
--
_______________________________________________
yocto mailing list
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto
Quoted 9 lines · Sinan Kaya
CC'ing the selinux maintainers:
I was told that using the master branch and reverting the e2fs change
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151)
works on sumo.Stefano's suggestion unfortunately didn't work.
Maybe, it is time to create the sumo branch?
Sorry, I thought it had been created. I'm going to be traveling the next few days to ELC-E, but I will try to get to it if someone else does not first.
--Mark
Quoted 59 lines · Steve Scott
Quoted 57 lines
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilationExactly the same issue since September.
Here is my discussion https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html. With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected] <mailto:[email protected]> > ha scritto:
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 26 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] <mailto:[email protected]> https://lists.yoctoproject.org/listinfo/yocto
Quoted 7 lines · [Re: [yocto] [selinux] sumo compilation] On 18.10.18 (Thu 11:00) Mark Hatle…
Quoted 6 lines · Sinan Kaya
CC'ing the selinux maintainers:
I was told that using the master branch and reverting the e2fs change
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151)
works on sumo.
Quoted 7 lines
Quoted 3 lines
Stefano's suggestion unfortunately didn't work.
Maybe, it is time to create the sumo branch?
Sorry, I thought it had been created. I'm going to be traveling the next few days to ELC-E, but I will try to get to it if someone else does not first.
Yeah, Mark and I are both going to be at ELC-E this week, we'll get it sorted out.
-J.
Quoted 63 lines
--Mark
Quoted 59 lines · Steve Scott
Quoted 57 lines
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilationExactly the same issue since September.
Here is my discussion https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html. With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected] <mailto:[email protected]> > ha scritto:
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 26 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] <mailto:[email protected]> https://lists.yoctoproject.org/listinfo/yocto
Quoted 5 lines · Joe MacDonald
Quoted 3 lines
Sorry, I thought it had been created. I'm going to be traveling the next few days to ELC-E, but I will try to get to it if someone else does not first.
Yeah, Mark and I are both going to be at ELC-E this week, we'll get it sorted out.
thanks.
Thank you
Il gio 18 ott 2018, 22:48 Sinan Kaya <[email protected]> ha scritto:
Quoted 9 lines · Joe MacDonald
Quoted 5 lines
Quoted 3 lines
Sorry, I thought it had been created. I'm going to be traveling the next few days to ELC-E, but I will try to get to it if someone else does not first.
Yeah, Mark and I are both going to be at ELC-E this week, we'll get it sorted out.
thanks.
I reverted the commit as described and finally I'm able to build.
However, after using -minimal version and booting with selinux=1 and enforcing=0, when I run this command: "fixfiles -f -F relabel" I get this error:
Cleaning out /tmp
fixfiles: No suitable file systems found
Cleaning up labels on /tmp
secon: SELinux is not enabled
cat: /initial_contexts/unlabeled: No such file or directory
I don't understand why it's happening.
I'm trying on the official iMX6 evaluation kit by NXP.
Il giorno gio 18 ott 2018 alle ore 23:13 Stefano Cappa < [email protected]> ha scritto:
Quoted 14 lines
Thank you
Il gio 18 ott 2018, 22:48 Sinan Kaya <[email protected]> ha scritto:
Quoted 9 lines · Joe MacDonald
Quoted 5 lines
Quoted 3 lines
Sorry, I thought it had been created. I'm going to be traveling the next few days to ELC-E, but I will try to get to it if someone else does not first.
Yeah, Mark and I are both going to be at ELC-E this week, we'll get it sorted out.
thanks.
Quoted 11 lines · Stefano Cappa
I reverted the commit as described and finally I'm able to build.
However, after using -minimal version and booting with selinux=1 and enforcing=0, when I run this command: "fixfiles -f -F relabel" I get this error:
Cleaning out /tmp
fixfiles: No suitable file systems found
Cleaning up labels on /tmp
secon: SELinux is not enabled
cat: /initial_contexts/unlabeled: No such file or directory
Quoted 3 lines
I don't understand why it's happening.
I'm trying on the official iMX6 evaluation kit by NXP.
You need to make sure that the filesystem in use has extendded attributes enabled. A lot of silicon vendor versions have this disabled, or use a filesystem where it's not supported.
ext*fs, xfs, etc usually support it, with the right kernel configuration.
--Mark
Quoted 17 lines
Il giorno gio 18 ott 2018 alle ore 23:13 Stefano Cappa <[email protected] <mailto:[email protected]>> ha scritto:
Thank you
Il gio 18 ott 2018, 22:48 Sinan Kaya <[email protected] <mailto:[email protected]>> ha scritto:
On 10/18/2018 3:08 PM, Joe MacDonald wrote:
>> Sorry, I thought it had been created. I'm going to be traveling the >> next few days to ELC-E, but I will try to get to it if someone else >> does not first.
> Yeah, Mark and I are both going to be at ELC-E this week, we'll get it > sorted out.thanks.
Hey all,
I just thought I should quickly follow up on this. I have a change set ready that includes tagging and a minor tweak for sumo, integration of the current outstanding patch list and a tag for thud and a couple of additional things (possibly) for post-thud. I'll send out a set for sumo and maybe an additional one for thud/post- possibly tomorrow or after I get home on Friday.
-J.
Quoted 93 lines · [Re: [yocto] [selinux] sumo compilation] On 18.10.18 (Thu 15:08) Joe MacDonald…
Quoted 7 lines · [Re: [yocto] [selinux] sumo compilation] On 18.10.18 (Thu 11:00) Mark Hatle…
Quoted 6 lines · Sinan Kaya
CC'ing the selinux maintainers:
I was told that using the master branch and reverting the e2fs change
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?id=78eca8242ea5397c4dc0654d62244453b4260151)
works on sumo.Quoted 7 lines
Quoted 3 lines
Stefano's suggestion unfortunately didn't work.
Maybe, it is time to create the sumo branch?
Sorry, I thought it had been created. I'm going to be traveling the next few days to ELC-E, but I will try to get to it if someone else does not first.
Yeah, Mark and I are both going to be at ELC-E this week, we'll get it sorted out.
-J.
Quoted 63 lines
--Mark
Quoted 59 lines · Steve Scott
Quoted 57 lines
I did not try it on sumo.
From: Stefano Cappa [mailto:[email protected]]
Sent: Wednesday, October 17, 2018 11:15 PM
To: [email protected]
Cc: Sinan Kaya <[email protected]>; [email protected]
Subject: Re: [yocto] [selinux] sumo compilationExactly the same issue since September.
Here is my discussion https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html. With that trick did you find a solution also on sumo?
Il gio 18 ott 2018, 01:42 <[email protected] <mailto:[email protected]> > ha scritto:
It was broken in rocko too. I added this to local.conf to workaround the problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Quoted 26 lines · ---- Sinan Kaya <[email protected] <mailto:[email protected]> > wrote:
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb <http://e2fsprogs_1.43.8.bb> :do_patch)
NOTE: recipe e2fsprogs-native-1.43.8-r0: taskdo_patch: Started
NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch)
NOTE: recipe e2fsprogs-1.43.8-r0: taskdo_patch: Started
ERROR: e2fsprogs-native-1.43.8-r0do_patch: Command Error: 'quilt --quiltrc
Applying patch misc_create_inode.c-label_rootfs.patch
patching filemisc/create_inode.c
Hunk #1 FAILED at 979.
Hunk #2 FAILED at 987.Sinan
Signature · 4 lines
_______________________________________________ yocto mailing list [email protected] <mailto:[email protected]> https://lists.yoctoproject.org/listinfo/yoctoSignature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Quoted 8 lines · Joe MacDonald
Hey all,
I just thought I should quickly follow up on this. I have a change set ready that includes tagging and a minor tweak for sumo, integration of the current outstanding patch list and a tag for thud and a couple of additional things (possibly) for post-thud. I'll send out a set for sumo and maybe an additional one for thud/post- possibly tomorrow or after I get home on Friday.
Thanks, we are looking forward to see it on yocto.
Quoted 2 lines
-J.
Are there any news about this? Also for thud branch.
Il mar 30 ott 2018, 14:46 Sinan Kaya <[email protected]> ha scritto:
Quoted 21 lines · Joe MacDonald
Quoted 8 lines
Hey all,
I just thought I should quickly follow up on this. I have a change set ready that includes tagging and a minor tweak for sumo, integration of the current outstanding patch list and a tag for thud and a couple of additional things (possibly) for post-thud. I'll send out a set for sumo and maybe an additional one for thud/post- possibly tomorrow or after I get home on Friday.
Thanks, we are looking forward to see it on yocto.
Quoted 2 lines
-J.
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
I have both ready to go, there's been a few hiccups with my access to the git server. I'll push my queued changes somewhere public when I get to a keyboard later today so at least everyone can see what's coming.
-J.
On Dec 30, 2018 6:29 AM, Stefano Cappa <[email protected]> wrote:
Are there any news about this? Also for thud branch.
Il mar 30 ott 2018, 14:46 Sinan Kaya <[email protected]<mailto:[email protected]>> ha scritto:
Quoted 8 lines · Joe MacDonald
Hey all,
I just thought I should quickly follow up on this. I have a change set ready that includes tagging and a minor tweak for sumo, integration of the current outstanding patch list and a tag for thud and a couple of additional things (possibly) for post-thud. I'll send out a set for sumo and maybe an additional one for thud/post- possibly tomorrow or after I get home on Friday.
Thanks, we are looking forward to see it on yocto.
Quoted 2 lines
-J.
--
_______________________________________________
yocto mailing list [email protected]<mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto
Quoted 3 lines · Joe
I have both ready to go, there's been a few hiccups with my access to the git server. I'll push my queued changes somewhere public when I get to a keyboard later today so at least everyone can see what's coming.
Update on this. While we're sorting out the access issue, the current master, sumo and thud branches on my personal mirror
(https://github.com/joeythesaint/meta-selinux) are mostly up-to-date (the only thing I haven't included in there yet is the refpolicy update for the 20180114 release, little overdue, that) and build for the respective Yocto releases. If that's not your experience, please let me know and we'll get that sorted out right away.
Thanks.
-Joe.
Quoted 35 lines
-J.
On Dec 30, 2018 6:29 AM, Stefano Cappa <[email protected]> wrote:
Are there any news about this? Also for thud branch.Il mar 30 ott 2018, 14:46 Sinan Kaya <[email protected]> ha scritto:
On 10/24/2018 7:49 PM, Joe MacDonald wrote:
> Hey all,
>
> I just thought I should quickly follow up on this. I have a change set > ready that includes tagging and a minor tweak for sumo, integration of > the current outstanding patch list and a tag for thud and a couple of > additional things (possibly) for post-thud. I'll send out a set for > sumo and maybe an additional one for thud/post- possibly tomorrow or > after I get home on Friday.Thanks, we are looking forward to see it on yocto.
>
> -J.--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoSignature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
One additional quick note, in hope of avoiding any further confusion, I'm working on the refpolicy version from July not January 2018. Sorry about that.
-J.
________________________________________
From: [email protected] <[email protected]> on behalf of MacDonald, Joe
Sent: Sunday, December 30, 2018 9:46 PM
To: Stefano Cappa
Cc: [email protected]
Subject: Re: [yocto] [selinux] sumo compilation
Quoted 3 lines · Joe
I have both ready to go, there's been a few hiccups with my access to the git server. I'll push my queued changes somewhere public when I get to a keyboard later today so at least everyone can see what's coming.
Update on this. While we're sorting out the access issue, the current master, sumo and thud branches on my personal mirror
(https://github.com/joeythesaint/meta-selinux) are mostly up-to-date (the only thing I haven't included in there yet is the refpolicy update for the 20180114 release, little overdue, that) and build for the respective Yocto releases. If that's not your experience, please let me know and we'll get that sorted out right away.
Thanks.
-Joe.
Quoted 35 lines
-J.
On Dec 30, 2018 6:29 AM, Stefano Cappa <[email protected]> wrote:
Are there any news about this? Also for thud branch.Il mar 30 ott 2018, 14:46 Sinan Kaya <[email protected]> ha scritto:
On 10/24/2018 7:49 PM, Joe MacDonald wrote:
> Hey all,
>
> I just thought I should quickly follow up on this. I have a change set > ready that includes tagging and a minor tweak for sumo, integration of > the current outstanding patch list and a tag for thud and a couple of > additional things (possibly) for post-thud. I'll send out a set for > sumo and maybe an additional one for thud/post- possibly tomorrow or > after I get home on Friday.Thanks, we are looking forward to see it on yocto.
>
> -J.--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Ok thank you, I'll try it.
Il giorno lun 31 dic 2018 alle ore 03:52 MacDonald, Joe < [email protected]> ha scritto:
Quoted 78 lines
One additional quick note, in hope of avoiding any further confusion, I'm working on the refpolicy version from July not January 2018. Sorry about that.
-J.
________________________________________
From: [email protected] <[email protected]> on behalf of MacDonald, Joe
Sent: Sunday, December 30, 2018 9:46 PM
To: Stefano Cappa
Cc: [email protected]
Subject: Re: [yocto] [selinux] sumo compilation[Re: [yocto] [selinux] sumo compilation] On 18.12.30 (Sun 14:31)
Quoted 1 line · Joe
I have both ready to go, there's been a few hiccups with my access to
the git
Quoted 1 line
server. I'll push my queued changes somewhere public when I get to a
keyboard
Quoted 1 line
later today so at least everyone can see what's coming.
Update on this. While we're sorting out the access issue, the current master, sumo and thud branches on my personal mirror
(https://github.com/joeythesaint/meta-selinux) are mostly up-to-date (the only thing I haven't included in there yet is the refpolicy update for the 20180114 release, little overdue, that) and build for the respective Yocto releases. If that's not your experience, please let me know and we'll get that sorted out right away.Thanks.
-Joe.
Quoted 4 lines
-J.
On Dec 30, 2018 6:29 AM, Stefano Cappa <[email protected]>
Quoted 8 lines · wrote:
Are there any news about this? Also for thud branch.
Il mar 30 ott 2018, 14:46 Sinan Kaya <[email protected]> ha scritto:
On 10/24/2018 7:49 PM, Joe MacDonald wrote:
> Hey all,
>
> I just thought I should quickly follow up on this. I have achange set
Quoted 1 line
Quoted 1 line
ready that includes tagging and a minor tweak for sumo,
integration of
Quoted 1 line
Quoted 1 line
the current outstanding patch list and a tag for thud and a couple
of
Quoted 1 line
Quoted 1 line
additional things (possibly) for post-thud. I'll send out a set
for
Quoted 1 line
Quoted 1 line
sumo and maybe an additional one for thud/post- possibly tomorrow
or
Quoted 19 lines
Quoted 1 line
after I get home on Friday.
Thanks, we are looking forward to see it on yocto. > > -J. -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
I tried with yocto thud and your repo (thud branch) and I can build without issues.
However when I try to run "fixfiles -f -F relabel" the result is:
**Cleaning out /tmp*
**fixfiles: No suitable file systems found*
**Cleaning up labels on /tmp*
**cat: /initial_contexts/unlabeled: No such file or directory* **secon: SELinux is not enabled*
I tried to check If I have xattrs in my ext4 partition and I can run these commands as suggested here https://bbs.archlinux.org/viewtopic.php?id=176400
:
$ touch testfile $ getfattr -n user.comment testfile testfile: user.comment: No such attribute $ getfattr testfile $ setfattr -n user.comment -v "this is a comment" testfile $ getfattr testfile # file: testfile user.comment
$ getfattr -n user.comment testfile # file: testfile user.comment="this is a comment"
$ setfattr -x user.comment testfile $ getfattr testfile
My config.gz contains these:
# CONFIG_IP_NF_SECURITY is not set
# CONFIG_IP6_NF_SECURITY is not setCONFIG_EXT2_FS_SECURITY=yCONFIG_EXT3_FS_SECURITY=yCONFIG_EXT4_FS_SECURITY=yCONFIG_SECURITY_DMESG_RESTRICT=yCONFIG_SECURITY=yCONFIG_SECURITYFS=yCONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
# CONFIG_SECURITY_PATH is not setCONFIG_SECURITY_SELINUX=y
# CONFIG_SECURITY_SELINUX_BOOTPARAM is not set
# CONFIG_SECURITY_SELINUX_DISABLE is not setCONFIG_SECURITY_SELINUX_DEVELOP=yCONFIG_SECURITY_SELINUX_AVC_STATS=yCONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=0
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
# CONFIG_SECURITY_YAMA is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not setCONFIG_DEFAULT_SECURITY_DAC=yCONFIG_DEFAULT_SECURITY=""
Is there a way to debug this issue with some tricks? Am I missing something?
Thank u.
Il giorno mer 9 gen 2019 alle ore 21:55 Stefano Cappa < [email protected]> ha scritto:
Quoted 83 lines
Ok thank you, I'll try it.
Il giorno lun 31 dic 2018 alle ore 03:52 MacDonald, Joe < [email protected]> ha scritto:
Quoted 78 lines
One additional quick note, in hope of avoiding any further confusion, I'm working on the refpolicy version from July not January 2018. Sorry about that.
-J.
________________________________________
From: [email protected] <[email protected]> on behalf of MacDonald, Joe
Sent: Sunday, December 30, 2018 9:46 PM
To: Stefano Cappa
Cc: [email protected]
Subject: Re: [yocto] [selinux] sumo compilation[Re: [yocto] [selinux] sumo compilation] On 18.12.30 (Sun 14:31)
Quoted 1 line · Joe
I have both ready to go, there's been a few hiccups with my access to
the git
Quoted 1 line
server. I'll push my queued changes somewhere public when I get to a
keyboard
Quoted 1 line
later today so at least everyone can see what's coming.
Update on this. While we're sorting out the access issue, the current master, sumo and thud branches on my personal mirror
(https://github.com/joeythesaint/meta-selinux) are mostly up-to-date (the only thing I haven't included in there yet is the refpolicy update for the 20180114 release, little overdue, that) and build for the respective Yocto releases. If that's not your experience, please let me know and we'll get that sorted out right away.Thanks.
-Joe.
Quoted 4 lines
-J.
On Dec 30, 2018 6:29 AM, Stefano Cappa <[email protected]>
Quoted 8 lines · wrote:
Are there any news about this? Also for thud branch.
Il mar 30 ott 2018, 14:46 Sinan Kaya <[email protected]> ha scritto:
On 10/24/2018 7:49 PM, Joe MacDonald wrote:
> Hey all,
>
> I just thought I should quickly follow up on this. I have achange set
Quoted 1 line
Quoted 1 line
ready that includes tagging and a minor tweak for sumo,
integration of
Quoted 1 line
Quoted 1 line
the current outstanding patch list and a tag for thud and a
couple of
Quoted 1 line
Quoted 1 line
additional things (possibly) for post-thud. I'll send out a set
for
Quoted 1 line
Quoted 1 line
sumo and maybe an additional one for thud/post- possibly tomorrow
or
Quoted 19 lines
Quoted 1 line
after I get home on Friday.
Thanks, we are looking forward to see it on yocto. > > -J. -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto